Priorities are determined by consistency.
priority is determined by [integrity
Developed with Scrapbox
You can't prioritize in the "things I want to do" state, and you can't force it.
/shokai/Scrapbox development - Real-time wiki built with React & Websocket.
Tasks are interrelated.
(Github Issues)relationship between multiple issues at different times.
/shokai/GitHub Discard Issue #58943ccd97c2910000e3e370
More features is a bad thing.
Combining general-purpose small features is the fun part!
Small features that can solve multiple requests
On the contrary, we want versatility that will give birth to uses not anticipated by the developer.
/shokai/tasks/efficiently-processing-tasks-is-fast-fucking-application-implementation.
/shokai/general-purpose-small-functions.
If you write information in the link notation field, such as "This is similar to that one, so maybe we can solve this together," a list of related pages will be generated.
/shokai/tasks/efficiently-processing-tasks-fast-implementing-fucking-applications#59d984de97c29100005622bc.
I thought this was related to the knowledge consistency I wrote on p.167 of The Intellectual Production of Engineers.
There is no "right answer" to "what should be prioritized" when there are multiple tasks.
This is similar to the state of not knowing if "knowledge" is "correct" or not.
It is the consistent theory of truth (theism) that brings in the criterion "knowledge that is coupled without contradiction with more things is more credible" in that state.
mitoujr2021.icon
#Consistent binding → associations → Interference Effects of Ideas in iterative KJ method.
---
This page is auto-translated from /nishio/優先順位が整合性によって決まる. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.